@lmolkova i had gone and addressed the controversial points which entered around polluting signals pages with deprecated attributes. This pr makes no changes to which attributes are rendered hence I saw that as closed. It also doesn't introduce a new concept. After which I did raise it at a semconv meeting the other week and the feedback I got was to avoid needing to consolidate yaml files which was also implemented.

As it stands the changes introduced here are just:

• render deprecated attributes under the same heading as the non-deprecated siblings but in a different section. This is mostly used in the registry.
• use a reduced/tailored table for deprecated attributes to remove un-necessary content and be able to link to new attribute where appropriate.

thanks for the explanation. Not needing to separate deprecated from active will indeed be useful with schema v2 where we won't have groups anymore. Most of jinja work will need to be redone at that time anyway.

I don't believe changes in markdown are beneficial though. And I'd postpone jinja work until we have a need (schema v2).

Would it not be beneficial to extend this PR to also flatten the groups now hence simplifying the jinja changes and get users use to no Grouping. That way when switching to v2 the generated markdown would hopefully not need to change.

By having the different layout we can reduce the amount of content being produced and we could even remove the example values if desired to further simplify it.